Multi-chassis inter-process communication

ABSTRACT

Aggregation Switches connected via a virtual fabric link (VFL) are each active and able to communicate via an inter-process communication (IPC) using an IPC Virtual Local Area Network (IPC VLAN). A sub-set of Customer-facing ports (CFPs) of each Aggregation Switch are coupled to the VFL and assigned to the IPC VLAN to enable communication therebetween.

CROSS-REFERENCE TO RELATED PATENTS

The present U.S. Utility patent application claims priority pursuant to 35 U.S.C. §119(e) to U.S. Provisional Application Ser. No. 61/370,622, entitled, “MULTI-CHASSIS VIRTUAL-FABRIC LINK AGGREGATION SYSTEM,” filed Aug. 4, 2010, which is incorporated by reference herein and made part of the present U.S. Utility patent application for all purposes.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not Applicable.

INCORPORATION-BY-REFERENCE OF MATERIAL SUBMITTED ON A COMPACT DISC

Not applicable.

BACKGROUND OF THE INVENTION

1. Technical Field of the Invention

This invention relates generally to data networks and in particular to systems and methods for providing IP multicast snooping and routing.

2. Description of Related Art

Data networks allow many different computing devices, for example, personal computers, IP telephony devices or servers to communicate with each other and/or with various other network elements or remote servers attached to the network. For example, data networks may comprise, without limitation, Metro Ethernet or Enterprise Ethernet networks that support multiple applications including, for example, voice-over-IP (VoIP), data and video applications. Such networks regularly include many interconnected nodes, commonly known as switches or routers, for routing traffic through the network.

The various nodes are often distinguished based on their location within particular areas of the network, commonly characterizing two or three “tiers” or “layers,” depending on the size of the network. Conventionally, a three tier network consists of an edge layer, an aggregation layer and a core layer (whereas a two tier network consists of only an edge layer and core layer). The edge layer of data networks includes edge (also called access) networks that typically provide connectivity from an Enterprise network or home network, such as a local area network, to a metro or core network. The edge/access layer is the entry point of the network, i.e., to which the customer network is nominally attached, and the switches residing at the edge layer are known as edge nodes. Different types of edge networks include digital subscriber line, hybrid fiber coax (HFC) and fiber to the home. Edge nodes may perform, for example, L2 switching functions for the attached devices. The edge nodes are generally connected to an aggregate layer that terminates access links coming from multiple edge nodes. Switches residing at the aggregation layer are known as Aggregation Switches. Aggregation Switches may perform, for example, L2 switching and L3 routing of traffic received via the aggregate links from the edge nodes. The aggregate layer is connected to a metro or core network layer that performs Layer 3/IP routing of traffic received from the Aggregation Switches (in a three tier network) or from edge nodes (in a two tier network). As will be appreciated, nodes at each incremental layer of the network typically have larger capacity and faster throughput.

One of the key challenges faced by data networks is the need for network resiliency, i.e., the ability to maintain high availability despite eventual component failures, link failures or the like, which is critical to providing satisfactory network performance. Network resiliency may be achieved in part through topological redundancy, i.e., by providing redundant nodes (and redundant components within nodes) and multiple physical paths between nodes to prevent single points of failure, and in part through L2/L3 protocols to exploit the redundancy upon occurrences of failures to converge upon alternate paths for switching/routing traffic flows through the network. As will be appreciated, detection and convergence times must occur quickly (advantageously, less than one second) to achieve seamless transition to the alternate paths.

Ethernet protocol is a transport technology that is used ubiquitously in local area networks (LAN), such as the home and enterprise networks to communicate between computers and networks. However, the use of Ethernet protocol technology in access and aggregate networks, as well as metro networks, is continuing to rise and to revolutionize the edge network as it did the enterprise network. As an access technology, Ethernet offers significant advantages over other access technologies, such as: (i) future-proof transport for data, video and voice applications; (ii) cost-effective infrastructure for data services; and (iii) simple, globally accepted standard that will ensure interoperability.

In order to adapt Ethernet technology to a carrier-grade service environment in edge and aggregate layer networks, a number of issues remain to be addressed, including resiliency to failures. In one known solution, the spanning tree protocol (STP) is commonly used to detect failures and divert traffic to alternate paths when failures occur in Ethernet networks. Generally, STP relies on multiple physical paths between switches, but with only one path active at any one time, the other path being placed in a blocking mode (defining an “active/passive” paradigm). When failures occur, an alternative path is brought out of the blocking mode into an active state, thereby re-establishing the connection.

However, STP can result in unacceptable convergence times (e.g., up to several seconds) in some network topologies, including without limitation, convergence between edge nodes and Aggregation switches of a data network. Further, STP provides only for an active/passive operation paradigm whereby not all links are actively forwarding traffic at the same time.

In an active-active environment, as described in co-pending U.S. patent application Ser. No. 13/010,168, filed Jan. 20, 2011, in which all paths are simultaneously active on redundant Aggregation switches, the convergence time can be greatly reduced. However, in order to allow multiple Aggregation switches to cooperate in such a multi-chassis system, the Aggregation switches may need to exchange control information to ensure proper routing and switching between the Aggregation switches and the edge nodes.

In particular, some of the software components running on one Aggregation Switch may need to exchange control information with counterpart/peer applications running on the remote Aggregation Switch. To accomplish this, both the physical and logical inter-process communication currently used internally within an Aggregation Switch needs to be extended to include both Aggregation Switches.

Accordingly, there is a need for systems and methods for providing inter-process communication within a multi-chassis system.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 illustrates a schematic block diagram of an embodiment of a network architecture in accordance with the present invention;

FIG. 2 illustrates a schematic block diagram of an embodiment of a multi-chassis system in accordance with the present invention;

FIG. 3 illustrates a schematic block diagram of an embodiments of Aggregation Switches in a multi-chassis system in accordance with the present invention;

FIG. 4 illustrates a schematic block diagram of an embodiment of a network interface module of an Aggregation Switch in a multi-chassis system in accordance with the present invention;

FIG. 5 illustrates a schematic block diagram of an embodiment of packet flow through an Aggregation Switch in a multi-chassis system in accordance with the present invention;

FIG. 6 illustrates a schematic block diagram of an embodiment of source address learning in a multi-chassis system in accordance with the present invention;

FIG. 7 illustrates a schematic block diagram of another embodiment of source address learning in a multi-chassis system in accordance with the present invention;

FIG. 8 illustrates a schematic block diagram of another embodiment of Aggregation Switches in a multi-chassis system in accordance with the present invention;

FIG. 9 illustrates a schematic block diagram of an embodiment of a pre-pended header of a packet in the multi-chassis system in accordance with the present invention;

FIG. 10 illustrates a schematic block diagram of an embodiment for managing inter-process communication within an Aggregation Switch in accordance with the present invention; and

FIG. 11 illustrates a schematic block diagram of an embodiment for implementing inter-processes communication between the Aggregation Switches in accordance with the present invention; and

FIG. 12 illustrates a schematic block diagram of an embodiment for performing inter-process communication between the Aggregation Switches in accordance with the present invention.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 illustrates an embodiment of a resilient network 100 with multi-chassis link aggregation that provides an active/active paradigm (i.e., all links actively forwarding traffic at the same time) that more fully utilizes the capacity of the network nodes. The following abbreviations are herewith defined:

-   CMM Chassis Management Module -   IGMP Internet Group Management Protocol -   IP Internet Protocol -   IPMS Internet Protocol Multicast -   LAG Link Aggregation -   L2 Layer 2 (“Data Link Layer”) of the OSI model for networks -   L3 Layer 3 (“Network Layer”) of the OSI model for networks -   MAC Media Access Control Protocol -   MC-LAG Multi-Chassis Link Aggregate Group -   MC-VFA Multi-Chassis Virtual Fabric Aggregation -   NIM Network Interface Module -   STP Spanning Tree Protocol -   VLAN Virtual Local Area Network -   VRRP Virtual Router Redundancy Protocol -   ASIC Application Specific Integrated Circuit

The following standards are referred to in this application and are incorporated by reference herein: 1) the Link Aggregation Control Protocol (LACP) which was formerly clause 43 of the IEEE 802.3 standard added in March 2000 by the IEEE 802.3ad task force and is currently as incorporated in IEEE 802.1AX-2008 on Nov. 3, 2008; and 2) IEEE Std. 802.1Q, Virtual Bridged Local Area Networks, 2003 edition.

The LACP provides a method to control the bundling of several physical links, called a link aggregation group (LAG), between two peer nodes to form a single logical channel there between. The peer nodes negotiate the bundling of the physical links into a LAG by exchanging LACP packets, or alternatively the LAG can be configured manually. Link aggregation offers an inexpensive way to transfer more data than any one single port or link can deliver alone. In an embodiment, the ports of a LAG include the same physical type, such as all copper ports (CAT-5E/CAT-6), all multi-mode fiber ports (SX), or all single-mode fiber ports (LX). In another embodiment, the ports of a LAG may have a different physical type.

To provide increased resiliency and remove a single point of failure, a LAG is split across two devices as seen in FIG. 1 and is referred to herein as a multi-chassis link aggregation group (MC-LAG) 102. For example, in FIG. 1, MC-LAG 102 a originates from edge node 104 and is split into two subsets and connected to two Aggregation Switches 106 a and 106 b, with one or more physical links of the MC-LAG 102 a in each subset. In an embodiment, the edge node 104 may use load balancing techniques to distribute traffic across all available links of the MC-LAG 102 a. For each packet transmitted over the MC-LAG 102 a, one of the physical links is selected based on a load-balancing algorithm (usually involving a hash function operating on the source and destination Internet Protocol (IP) or Media Access Control (MAC) address information). Load balancing across the physical links of the MC-LAG 102 results in a more effective use of bandwidth.

As seen in FIG. 1, the edge node 104 is connected over an access network 122 to an enterprise network device 110, such as a bridge, switch, router, etc., that is operating in a LAN, and/or it may also be connected to a home network device 112, such as a DSL modem, set-top box, optical line terminal, etc. The edge node 104 is a switch or server and may functionally include a digital subscriber line access multiplexer (DSLAM), cable modem termination system (CMTS), optical line terminal (OLT), etc. in an embodiment but may include other types of devices as well.

In an embodiment, the Aggregation Switches 106 are coupled with a virtual fabric link (VFL) 124. The VFL 124 provides a connection for exchange of information between the Aggregation Switches regarding traffic forwarding, MAC addressing, multicast flows, address resolution protocol (ARP) tables, Layer 2 control protocols (e.g. spanning tree, Ethernet ring protection, logical link detection protocol), routing protocols (e.g. RIP, OSPF, BGP) and the status of the MC-LAG 102 a. The Aggregation Switches 106 operate transparently to the edge node 104 and are treated as a single logical device by the edge node 104. The edge node 104 is able to actively forward traffic on the MC-LAG 102 a while the synchronization of MAC address tables and other forwarding information between the Aggregation Switches 106 is driven by L2 packet flows over the VFL along with a reduced amount of control messaging in an embodiment. This feature enables dual homing of the edge node 104 to the pair of Aggregation Switches 106 and provides a Layer 2 multi-path intra-structure as well as basic Layer 3 access infra-structure. In addition, in an embodiment, the MC-VFA feature provides this functionality without requiring Layer 2 redundancy protocols (e.g. Spanning Tree) between the edge node 104 and Aggregation Switches 106, while still facilitating a carrier-grade detection and convergence time to edge uplink failures as well as aggregation/core switch failures. Many recent network designs, especially for data centers, are requiring an ever increasing number of layer 2 adjacencies between edge node and Aggregation Switches. This trend is pushing the limits of the spanning tree protocol, such as loop-detection function and convergence times. The spanning tree convergence time can be of up to several seconds in many current network topologies. The multi-chassis architecture in an embodiment provides a dual-homed, layer 2 multi-path connection between the edge node 104 and Aggregation Switches 106 preferably without needing to run the spanning tree protocol operation for loop prevention, while still being flexible enough to allow the spanning tree protocol operation along with the multi-chassis functionality in some of the portions of the network topology in an embodiment (e.g. between the Aggregation Switches over the virtual fabric link as well as over the links connecting these devices to upstream/core switches).

The feature in some embodiments also facilitates fast fail-over detection and convergence times for access uplink failures, virtual fabric link failures and node failures. Another advantage of the MC-VFA architecture in an embodiment is the active/active forwarding mode of the edge node 104 whereby both sets of operational MC-LAG uplinks are processing traffic to increase efficiency of the use of bandwidth of the MC-LAG links.

As seen in FIG. 1, in an embodiment, the Aggregation Switches 106 are also connected to a metro or core network 120 that includes one or more network nodes 116, such as network switches and/or routers, using the MC-LAG functionality (as part of the MC-VFA architecture) as described herein. For example, Aggregation Switch 106 b is connected to network nodes 116 b and 116 c over MC-LAG 102 b wherein the network nodes 116 b and 116 c exchange state information over a VFL as well. The MC-LAG 102 b architecture provides a dual-homed, layer 2 multi-path connection between the aggregation switch 106 b and network nodes 116 b and 116 c. In an embodiment, network nodes 116 can also be connected using MC-LAG functionality, as seen with MC-LAG 102 c and VFL 124. The Aggregation Switches 106 may also be connected to the network nodes 116 using a standard LAG, such as LAG 118, or other trunks or links.

The MC-VFA architecture is now described in more detail with respect to FIG. 2. Edge node 104 a is connected to Aggregation Switches 106 a and 106 b by a first MC-LAG1 102 a while edge node 104 b is connected to Aggregation Switches 104 a and 104 b by second MC-LAG2 102 b. Each MC-LAG 102 a and 102 b includes a plurality of physical links divided into at least two subsets, wherein each of the two subsets includes at least one physical link. As seen in FIG. 2, the first set of MC-LAG 102 a physical links are terminated at a first Aggregation Switch 106 a while the second set of MC-LAG 102 a physical links are terminated at a second Aggregation Switch 106 b. MC-LAG1 forms logical dual homed, layer 2 multi-paths. The MC-LAG member ports are the external, user ports that are members of the MC-LAG 102. The VFL 124 is an aggregate of ports that in an embodiment span multiple network interface modules for resiliency and provides for inter-chassis traffic and control/state data transfer. The multi-chassis system 140 includes the Aggregation Switches 106, the virtual fabric link 124, the MC-LAG 102 a, the MC-LAG 102 b and their respective MC-LAG member ports attached to the downstream edge devices. The Aggregation Switches 106 a and 106 b are separate physical switches with each operable as a stand-alone switch and each encased by its own separate physical chassis. The Aggregation Switches 106 a and 106 b may be in the same geographic area, such as in a central office or data center, or may be separate geographic locations, such as different buildings or cities, to provide geo diversity.

The edge nodes 104 operating as MC-LAG clients attached to the Aggregation Switches can use different methods to assign traffic to the links within their aggregates as long as the choice of links remains fixed for a given flow. This ensures that traffic is delivered in-sequence between any pair of communicating end stations. In an embodiment, the same number of uplink ports from the edge devices to each one of the MC-LAG Aggregation Switches should preferably be configured. In other words, if two uplinks are configured between the edge switch and one of the MC-LAG Aggregation Switches, then two uplinks between the edge switch and the other multi-chassis switch should also be configured. Although not mandatory, this arrangement provides a more homogeneous traffic distribution for flows between the multi-chassis switches and the edge device.

The Virtual fabric link (VFL) 124 between the Aggregation Switches 106 is now described in more detail with respect to FIG. 3. The Aggregation Switches 106 in one embodiment each include at least one CMM module 150 a (primary) and preferably a second CMM module 150 b (back-up) as well as a plurality of Network Interface modules (NIM) 152, such as line cards or port modules. The VFL 124 is an aggregate of VFL member ports connected to one or more NIMs 152, in the first and second Aggregation Switches 106. For example, VFL 124 includes a first subset A of physical links between NIM 152 a of Aggregation Switch 106 a and NIM 152 b of Aggregation Switch 106 b, and a second subset B of physical links between NIMs 152 n of Aggregation Switch 106 a and 106 b. In an embodiment, the VFL links are connected between Switching ASICs 210 residing in the NIMs 152 of the Aggregation Switches 106. The NIMs 152 each also include a Queuing ASIC 212, described further below. A switching fabric inter-connect (IC) 214 provides an interconnection between the various NIMs 152 in the Aggregation Switch 106.

A unique chassis identifier is assigned to each Aggregation Switch 106 in the multi-chassis system. The Chassis ID for each Aggregation Switch 106 is unique and global, e.g. each Aggregation Switch is aware of the chassis ID of its peer Aggregation Switch. Unique hardware device identifiers (MIDs) for various components, such as IC, NIM, CMM, in each Aggregation Switch are also generated allowing for management of local and remote objects. In an embodiment, the hardware device identifiers for the Switching ASICs 210 have global significance within the multi-chassis system while MIDs for other components, such as Queuing ASICs 212, may have only local significance. For example, the hardware device identifiers' assigned to the Switching ASICs 210 are known by both Aggregation Switches 106 while hardware device identifiers for other devices are restricted to a local Aggregation Switch and have no significance to the remote Aggregation Switch.

In an embodiment, the Switching ASICs 210 are assigned a global unique hardware device identifier (MID) in a range assigned to its Aggregation Switch, such as:

Aggregation Switch 106 a: Chassis ID=1 and MID values 0-31

Aggregation Switch 106 b: Chassis ID=2 and MID values 32-63

Exemplary MIDs assigned to Switching ASICs 210 are shown in FIG. 3. By knowing the assigned range, a module is able to determine the location of a switching ASIC from its MID as in Aggregation Switch 106 a or Aggregation Switch 106 b. In an embodiment, the Switching ASICs 210 operate in a pre-pended header mode to exchange data and control packets between the Aggregation Switches 106.

FIG. 4 illustrates a schematic block diagram of an embodiment of a network interface module (NIM) 152 in more detail. The Switching ASIC 210 includes a plurality of external port interfaces 240 that are connected to external nodes, such as edge nodes 104 a and 104 b. One or more of the external port interfaces 240 may include member ports for a MC-LAG physical link, LAG or other trunk group, fixed link, etc. The external ports 240 may have the same physical interface type, such as copper ports (CAT-5E/CAT-6), multi-mode fiber ports (SX) or single-mode fiber ports (LX). In another embodiment, the external ports 240 may have one or more different physical interface types.

The external ports 240 are assigned external port interface identifiers (Port ID), e.g., device port values, such as gport and dport values, associated with the Switching ASICs 210. In an embodiment, MIDs of the Switching ASICs 210 and external port interface identifiers for external ports 240 on the Switching ASICs 210 are used to uniquely identify a physical external port interface 240 of a Switching ASIC 210 on either the local or remote Aggregation Switch in the multi-chassis system. In another embodiment, a Port Manger that includes a conversion module or other entity may convert the MIDs of the Switching ASICs 210 and external port identifiers into a single integer value, to generate a global port value (GPV), e.g. MID 4; device port identifier (dport) 5 converts to GPV 20. In either example, unique external port identifiers for the external ports of NIMs 152 in both the local and remote Aggregation Switches are generated. Unique port identifiers may also be assigned to internal ports of a Switching ASIC 210, such as an internal port from the Switching ASIC 210 to a processing module on the NIM 152. These internal ports are also uniquely identified by the port identifier and the MID of the Switching ASIC.

The Switching ASIC 210 further includes a packet management unit (PMU) 242 that determines a destination address of incoming packets. The packets may be switched to another external port interface 240 of the Switching ASIC 210, to the Queuing ASIC 212 for transmission to another NIM 152 on the local or remote Aggregation Switch, or to the processor interface (PI) 244 for transmission to a processing module 266 of the NIM 152 external or internal to the Switching ASIC 210.

When a packet is to be transmitted to another NIM 152 on the local or remote Aggregation Switch, in an embodiment, the Switching ASIC 210 transfers the packet to a pre-pended packet header interface (PPHI) that adds or otherwise modifies the packet header to include hardware device information (HDI). The HDI includes identifiers of hardware devices associated with the source and/or the destination of the packet. In an embodiment, the pre-pended header may include other information such as packet priority and load balance identifiers. To obtain destination HDI information, the PPHI performs a look-up process to MAC/HDI forwarding table 250. The MAC/HDI forwarding table 250 stored in the address table memory 248 includes a list of MAC address entries, such as MAC address for external devices, nodes, modules, software or hardware connected to the Aggregation Switch 106. The MAC address entries include associated hardware device information used in bridging or routing a packet to reach a device with the associated MAC address. The destination hardware device information includes, for example, the port identifier and MID of a Switching ASIC 210 (e.g. MID=24, port ID=5 or MID=54, device port=12), of either the local or peer Aggregation Switch, associated with the destination MAC address. In another embodiment, the destination hardware device information may include the global port value (GPV) of the external port interface associated with the destination MAC address. The MAC/HDI forwarding table 250 may include one or more tables, such as source trunk map, trunk bitmap table, trunk group tables, VLAN mapping table, etc. In an embodiment, the MAC/HDI forwarding table 250 or parts thereof may be located in the Queuing ASIC of the NIM 152 as well.

In an embodiment, when the Switching ASIC 210 includes an active VFL member port 252 with a link to the remote Aggregation Switch, the MAC/HDI forwarding table 250 may include additional HDI information, such as a table to associate gport values into Switching ASIC MID values and device port values and/or a table with logical aggregate group identifiers mapping to external port interfaces.

In an embodiment, the pre-pended header includes hardware device information HDI associated with the source port, such as an external or internal port interface, including hardware device identifier MID of the Switching ASIC and device port identifier of the source port.

In another embodiment, the pre-pended header includes HDI associated with a Switching ASIC 210 connected to the VFL port 124 (such as MID=0 or MID=31 for Aggregation Switch 106 a in FIG. 3). The Switching ASIC 210 connected to the VFL port will then translate or convert the HDI in the pre-pended header before transmitting the packet over the VFL.

In an embodiment, the PPHI 246 also appends source hardware device information associated with the source port, e.g. the external port interface 240 that first received the packet. The source hardware device information may include the MID of the Switching ASIC 210 and the port identifier (e.g., device port) and/or global port value (GPV) of the external port interface 240. Additional information, such as destination hardware device identifier or MID, a destination device port, VLAN ID, packet type (multicast, unicast, broadcast), packet priority and load balance identifier is also added to the pre-pended header in an embodiment. In an embodiment, the destination HDI is retrieved from the address tables 248, such as MAC/HDI forwarding table 250.

The packet with the pre-pended header is then transmitted to the Queuing ASIC 212 for routing over the Fabric IC 214. The Queuing ASIC 212 includes a packet buffer 260, a queue management 262 for providing traffic and buffer management and a global HDI address table 264. The global HDI address table 264 maps the destination HDI to the appropriate queues in Queuing ASICs 212 in one or more of the other NIMs 152. For example, the mapping provides information for switching the packet into an appropriate egress queue for one or more of the external port interfaces in other Queuing/Switching ASICs in the Aggregation Switch 106 based on the hardware device information in the pre-pended header. In another example, when the destination HDI indicates a destination on the remote Aggregation Switch (i.e. the destination device identifier belongs to a remote/peer switch range), the Queuing ASIC 212 switches the packet to an appropriate egress queue for one or more of the VFL port interfaces in the local Aggregation Switch 106 for transmission to the remote Aggregation Switch over the VFL 124, e.g. the global HDI address table 264 indicates that the associated hardware device is located on the remote Aggregation Switch. In this scenario, the determination of the egress queue corresponding to a particular VFL port interface is made based on the load balance identifier present in the pre-pended header and inserted previously by the switching ASIC 210.

Though the switching ASIC 210 and Queuing ASIC 212 are illustrated as separate integrated circuits or modules, one or more functions or components of the ASICs may be included on the other ASIC or combined into an alternate ASIC or otherwise be implemented in one or more integrated circuits.

FIG. 5 illustrates a schematic block diagram of an embodiment of a packet flow through Aggregation Switch 106 a to VFL 124. In this example, a device 300 with source MAC address, such as enterprise device 110 or home network device 112, transmits a packet, e.g. through edge node 104, to Aggregation Switch 106 a with a destination MAC address of a device that may be accessed over an external port interface of the remote Aggregation Switch 106 b. Switching ASIC 210 n, e.g. with MID=31 in FIG. 5, in NIM 152 n receives the packet on an external port interface 240, e.g. with port ID=2. The Switching ASIC 210 n extracts a destination MAC address and performs an address table look-up to determine hardware device information (HDI) associated with the destination MAC address from MAC/HDI forwarding table 250. The destination HDI may include, e.g., device module identifiers (MIDs) of one or more hardware components in a path to the destination device with the MAC address, such as NIMs 152, Queuing ASICs 212, Switching ASICS 210, external port identifiers 240, member ports of the VFL 124, of either the local Aggregation Switch 106 a or remote Aggregation Switch 106 b. In an embodiment, the destination HDI may include the MID of the Switching ASIC 210 and port identifier (e.g., device port) of the external port interface 240 that provides access to the destination device. Furthermore, in an embodiment, the pre-pended header includes a packet priority and a load balance identifier determined based on parameters retrieved from the original packet (source MAC address, destination MAC address, source IP address, destination IP address). In another example, the HDI would include a global port value (GPV) for the external port interface 240 or MID of the NIM 152 that provides access to the destination device. In another embodiment, when the destination MAC address is associated with the remote Aggregation Switch, the HDI may include the hardware device identifier MID for the NIM 152 a or Switching ASIC 210 (such as MID=0) connected to the VFL 124. The destination HDI is added to a pre-pended header that adds information to the original packet header (such as a layer 2, Ethernet packet header type). The Switching ASIC 210 n also includes source hardware device information (HDI) for one or more devices associated with the originating external port interface, e.g. port ID=2. The source HDI may include one or more hardware device identifiers, such as MID of the originating Switching ASIC 210, source port identifier (e.g. device port), global port value, MID for source NIM 152, Chassis ID, etc.

The packet with pre-pended header is transmitted to the Queuing ASIC 212 n which then determines a NIM 152 on the local Aggregation Switch to transmit the packet based on the destination HDI. When the destination HDI indicates a local external port interface on the Aggregation Switch 106 a (e.g. based on the destination MID contained in the pre-pended header), the Queuing ASIC 212 n places the packet in an egress queue for transmission to the corresponding NIM 152 of the local external port interface. In another example illustrated in FIG. 5, the Queuing ASIC 212 n determines that the destination HDI indicates a destination hardware device on the remote Aggregation Switch, e.g. the HDI indicates Switching ASIC with MID=45 on the remote Aggregation Switch. To reach the remote Aggregation Switch, the packet needs to be transmitted over the VFL 124. So, the Queuing ASIC 212 n transmits the packet with pre-pended header from a queue over the Fabric IC 214 to NIM 152 a connected to the VFL 124. The selection of a VFL member port is made based on the load balance identifier parameters carried on the pre-pended header. The Queuing ASIC 212 a on NIM 152 a receives the packet with pre-pended header and queues the packet for transmission over the VFL 124. The Switching ASIC 210 a then transmits the packet with pre-pended header including the source and/or destination HDI to the remote Aggregation Switch over the VFL 124.

In an embodiment, the Switching ASIC 210 a may alter the pre-pended header prior to transmission over the VFL 124. For example, the Switching ASIC 210 a may translate a destination HDI with local significance (e.g., a gport value or local hardware device identifier MID) to an HDI with global significance. The Switching ASIC 210 a then transmits the packet with pre-pended header including the source and/or destination HDI to the remote Aggregation Switch over the VFL 124.

In an embodiment, when multiple Switching ASICs 210 of an Aggregation Switch 106 are connected to the VFL 124, e.g. in FIG. 3, Switching ASICs MID=0 and MID=31, the traffic to be transmitted over the VFL 124 may be distributed. For example, a load balance identifier map table in the Global HDI Address Table 264 of the Queueing ASIC 212 would indicate the following distribution:

Destination MID Outgoing Port MID's Device Location  [0-31] VFL 124 Local [32-63] VFL 124 Remote

The Queueing ASICs 212 map the packets to the appropriate VFL port interface using the load balance identifiers or other load balancing techniques. For example, in an embodiment with 8 NIMs 152 on each Aggregation Switch, each Queuing ASIC 212 n has a set of 8 queues configured to each NIM (Module ID, Port) within the local Aggregation Switch. In an embodiment, the Queuing ASICs 212 connected to the Switching ASICs 210 with the VFL 124 have a separate set of 8 queues related to each VFL member port interface. Each of those queues is assigned to the FIFOs associated with the internal VFL ports connecting the multi-chassis switches. In an embodiment, with multiple Virtual Fabric Link member ports, the queues are assigned such that the destination ports on the remote chassis are equally distributed among the Queuing ASICs 212 a and 212 n that host the Virtual Fabric Link Member Ports.

In an embodiment, the MAC/HDI forwarding tables in the NIMs 152 are populated and then updated in response to layer 2 packets flowing through the system. Since the pre-pended header includes source MAC address and source HDI information, the NIMS 152, e.g. in specific the Switching ASICs 210 in an embodiment, are able to populate the MAC/HDI forwarding table 250 with this information. By operating in a pre-pended header mode to exchange Layer 2 packets with source MAC addresses and source HDI over the VFL 124, the Switching ASICs 210 are able to synchronize MAC address tables between the Aggregation Switches 106. Though the MAC/HDI forwarding table is described in the Switching ASICs 210, the MAC/HDI forwarding table may be included, alternatively or in addition to, in the Queuing ASICs 212 n or other module of the NIM 152. In another embodiment, the CMM 150 (primary and secondary) may also include a MAC/HDI forwarding table for one or more types of links between the Aggregation Switches 106.

FIG. 6 illustrates a schematic block diagram of an embodiment of a multi-chassis system that illustrates source MAC learning. Edge nodes 104 are connected to Aggregation Switches 106 a and 106 b over logical aggregate group LAG1 282, multi-chassis logical aggregate group MC-LAG1 102 a, multi-chassis logical aggregate group MC-LAG2 102 b and fixed port link 280. In an embodiment, each Aggregation Switch communicates to the other Aggregation Switch configuration information for logical aggregate groups, such as LAG1 and other types of trunk groups, and hardware device information associated thereto. In an embodiment, the hardware device information includes physical ports associated with the logical aggregate groups, e.g. hardware device or module identifiers (MID) of Switching ASICS and external port identifiers for links associated with the logical aggregate groups (device port values or gport values).

For example, in an embodiment, Aggregation Switch A notifies Aggregation Switch B that the logical aggregate group with aggregate group identifier LAG1 is associated with a Switching ASIC having a hardware device module identifier MID=31 and external port interface with identifier device port=1, 2. Aggregation Switch B notifies Aggregation Switch A that the logical aggregate group with aggregate group identifier MC-LAG1 is associated with a Switching ASIC having hardware device module identifier MID=45 and external port interface identifier device port=1, 2. Other hardware device information, such as identifiers of NIMs, Queuing ASICs, etc. associated with the logical aggregate groups may be exchanged alternatively or in addition to the Switching ASIC's MIDs and device port values. The Aggregation Switches 106 also provide notifications of updates to the configuration information of the logical aggregate groups for both ordinary aggregates and multi-chassis aggregate groups. The hardware device information associated with the logical aggregate groups and multi-chassis aggregates of either of the Aggregation Switches is included in one or more of the MAC/HDI forwarding tables in NIMs 152 on both Aggregation Switches. For example, in an embodiment, one or more of the MAC/HDI forwarding tables in both Aggregation Switches 106 includes the following information:

Type of HDI List of Aggregate Group Aggregate Group Identifier VFL Member Ports LAG LAG1 (MID = 31, Port ID = 1) (MID = 31, Port ID = 2) MC-LAG MC-LAG1 (MID = 31, Port ID = 3) (MID = 31, Port ID = 4) (MID = 45, Port ID = 1) (MID = 45, Port ID = 2) MC-LAG MC-LAG2 (MID = 31, Port ID = 5) (MID = 45, Port ID = 3)

Since the same aggregate group identifiers for logical aggregate groups (e.g. LAG1) are known and utilized by both Aggregation Switches 106, in an embodiment, the multi-chassis system assigns a subset of aggregate group identifiers to each type of logical group and for each of the Aggregation Switches 106. For example, in an embodiment with a maximum of 128 possible aggregate groups, an assignment of aggregate group identifiers would include:

Type of Aggre- Aggre- gate gation Range Group Switch Range Configuration Default Example LAG chassis MIN_LAG_ID_LOCAL [0-47]  [0-100] 1 MAX_LAG_ID_LOCAL LAG chassis MIN_LAG_ID_REMOTE [48-95]  [101-120] 2 MAX_LAG_ID_REMOTE MC- Both MIN_MC-LAG_ID [96-127] [121-127] LAG chassis MAX_MC-LAG_ID

The Aggregation Switches 106 assign aggregate group identifiers based on the assigned ranges and type of aggregate group. As such, packet forwarding in the Aggregation Switches is performed by accessing the MAC/HDI forwarding tables and using the mapping between the logical aggregate groups and hardware device information. Typically, aggregate identifier information is not transferred in the pre-pended headers.

In an embodiment, to facilitate load balancing over a LAG or MC-LAG, when an Aggregation Switch 106 receives a packet over the VFL 124 with destination HDI information, such as (MID, Port ID), the Aggregation Switch 106 determines whether the destination HDI is included in a logical aggregate group by searching for the port identified in the source HDI (destination MID, destination Port identifier) in one or more of its internal trunk tables that contain a list of all ports that are active members of each LAG or MC-LAG aggregate group. When a destination port is found in an associated LAG or MC-LAG, the Aggregation Switch 106 may perform load balancing techniques by assigning the packet to one or more different external port interfaces of the associated LAG. For example, when Switching ASIC 210 connected to the VFL in the remote Aggregation Switch 106 b receives a packet with destination HDI of MID=45, port 2, the switching ASIC 210 determines from its MAC/HDI table below, that MID=45, port 2 is part of MC-LAG1 as shown in the example in FIG. 6. The switching ASIC may then decide to perform load balancing and determine through one or more hash algorithms to transmit the packet over MID=45, port 1 of MC-LAG1 instead. In this particular example, the switching ASIC will then strip off the pre-pended header prior to transmitting the packet out of the external port (MID=45, port 1).

Aggregation Switch A LAG ID HDI LAG1 (MID = 31, Port ID = 1) (MID = 31, Port ID = 2) MC-LAG1 (MID = 31, Port ID = 3) (MID = 31, Port ID = 4) (MID = 45, Port ID = 1) (MID = 45, Port ID = 2) MC-LAG-2 (MID = 31, Port ID = 5) (MID = 45, Port ID = 3)

Referring back to FIG. 6, various embodiments of methods and implementations therefore are now described for learning source MAC addresses and associated hardware device information (HDI) in a multi-chassis system. First, in an embodiment, for unknown unicast packets ingressing on a configured fixed port of one of the Aggregation Switches (e.g. traffic originating on fixed port 280 with source MAC address=d1), the Source MAC address is populated in MAC/HDI forwarding tables on both Aggregation Switches 106 a and 106 b as associated with hardware device information (HDI) of the originating configured fixed port (such as MID of Switching ASIC and source port identifier value or gport value of the source port, NIM identifier, or other hardware device ID associated with the source port). As such, in an embodiment, the source MAC address d1 is stored in one or more MAC/HDI forwarding tables of both Aggregation Switch A and Aggregation Switch B with the VLAN ID and HDI associated with the source port, e.g., MID=45, Port ID=4.

Next, in an embodiment, unknown unicast traffic ingressing on a logical aggregate group connected to only one of the Aggregation Switches 106, such as a trunk group or other type of LAG (e.g. traffic originating on LAG1 with source MAC address=a1), the Source MAC address is populated in MAC/HDI forwarding tables on both Aggregation Switches 106 a and 106 b as associated with the originating logical aggregate group identifier (e.g., LAG1). As such, in an embodiment, the source MAC address a1 received on LAG1 by Aggregation Switch A is stored in one or more MAC/HDI forwarding tables of both the Aggregation Switches 106 with the VLAN ID and logical aggregate group identifier LAG1. In addition, as explained herein, the MAC/HDI forwarding tables of both Aggregation Switches store the hardware device information associated with logical aggregate groups (learned through distribution of configuration information by the CMM 150 module or other control plane process). The MAC/HDI forwarding tables thus include information that MAC address a1 is associated with trunk group identifier LAG1 and HDI information associated with LAG1.

Further, in an embodiment, for unknown unicast traffic ingressing on a MC-LAG member port (e.g. traffic originating on MC-LAG1 or MC-LAG2) of either Aggregation Switch 106, the Source MAC is populated in MAC/HDI forwarding tables as associated with the MC-LAG identifier and HDI information of the local member ports of the MC-LAG. The HDI information of the member ports of the MC-LAG will be the same for the MAC/LAG tables on each Aggregation Switch 106. In other words, both Aggregation Switches are fully aware of the entire list of member ports that are active participants of an MC-LAG aggregate group regardless of whether a member port is local or remote.

By associating member ports of a MC-LAG with a source MAC address, traffic destined to the MAC address through one of the edge nodes 104 is forwarded preferably via the MC-LAG member ports through the shortest path. This path reduces the amount of traffic crossing the VFL 124. In addition, it reduces MAC movement problems in some specific scenarios wherein traffic to and from an edge node 104 takes different paths over the MC-LAG for distinct flows. In the example of FIG. 6 in an embodiment, one or more of the MAC/HDI forwarding tables on the Aggregation Switches 106 includes the following information.

MAC LAG LAG ID Aggregation Switch A a1 Yes LAG1 b1 Yes MC-LAG1 c1 Yes MC-LAG-2 d1 No — Aggregation Switch B a1 Yes LAG1 b1 Yes MC-LAG1 c1 Yes MC-LAG-2 d1 No —

In another embodiment, MAC address tables displayed in a node or network management application may not include the HDI for the logical aggregation groups. The user displayed MAC address table may only include HDI for fixed ports and thus are similar for both Aggregation Switches 106.

Aggregation Switch A MAC LAG LAG ID HDI a1 Yes LAG1 N/A b1 Yes MC-LAG1 N/A c1 Yes MC-LAG-2 N/A d1 No — (MID = 45, Port ID = 4)

Aggregation Switch B MAC LAG LAG ID HDI a1 Yes LAG1 N/A b1 Yes MC-LAG1 N/A c1 Yes MC-LAG-2 N/A d1 No — (MID = 45, Port ID = 4)

The MAC/HDI forwarding tables are synchronized with respect to the LAG identifiers associated with the source MAC addresses. In addition, VLAN IDs associated with the MAC addresses may also be configured and synchronized on both Aggregation Switches. As such, logically, the Aggregation Switches 106 operate as a single bridge for MAC learning. Furthermore, MAC learning occurs automatically as traffic flows over the VFL 124 with minimum Layer 2/control module management software intervention and without the need for inter-process communication message-based MAC table synchronization.

FIG. 7 illustrates an embodiment of a method for source MAC learning in a multi-chassis system in more detail. To determine a MAC address for device B, device A 300 a (with MAC address=MAC_(A)) transmits a MAC address request, e.g. an address resolution packet (ARP) used in Ethernet protocols, with the target IP address for device B 300 b. For example, the MAC address request may include:

Source MAC=MAC_(A)

Destination MAC=ff:ff:ff:ff:ff:ff (unknown)

Target IP=IP_(B)

VLAN ID=ID

Packet Type=Broadcast.

When received by the edge node 104 a, it forwards the MAC address request over MC-LAG A to the “logical” Aggregation Switch 106 (composed of two physical switches 106 a and 106 b). Depending on the load balancing or hashing algorithm, the edge node 104 a may transmit the MAC address request over either of the subsets of physical links of MC-LAG A, either L_(A1) or L_(A2). For this example, assume that the MAC address request is transmitted over L_(A1) connected to Aggregation Switch 106 a. In general, in an Ethernet switch, a MAC address request (such as ARP) is copied and broadcast over every port associated with the VLAN ID. In an embodiment, when Aggregation Switch 106 a receives the MAC address request, it first appends a pre-pended header to the MAC address request with source logical aggregate group identifier (e.g., MC-LAG A) and/or source HDI (e.g., MID=12, port ID=1). The Aggregation Switch (e.g., in specific switching ASIC MID=12) then broadcasts copies of the packet with pre-pended header to each Switching ASICs with external port interfaces associated with the VLAN ID, such as Switching ASIC MID=31 in this example. The Switching ASICs on the Aggregation Switch 106 a (e.g. MID=12, MID=31) receiving the MAC address request with pre-pended header then learn the source MAC address and the associated aggregate group identifier (either explicitly present in the pre-pended header or by searching for the source HDI information in its trunk tables, which contain the complete list of MC-LAG A's member ports as described herein, e.g., MID=12, Port IDs=1,2 and MID=45, Port IDs=1,2) and are able to populate their MAC/HDI forwarding table with the aggregate group identifier information. For example, Switching ASIC MID=31 enters into its MAC/HDI forwarding table that source MAC address MAC_(A) is associated with logical aggregate group MC-LAG A and/or with HDI of source port MID=12, port ID=1 depending on the specific embodiment. Prior to transmitting the MAC address request from external port interfaces to edge node B, Aggregation Switch 106 a (e.g. Switching ASIC with MID=31) removes the pre-pended header thus retains an Ethernet or IP protocol header.

The Aggregation Switch 106 a also transmits the broadcast packet with pre-pended header over the VFL 124 to Aggregation Switch 106 b. The Aggregation Switch 106 b also learns the source MAC address and associated aggregate group identifier and/or source HDI from the broadcast packet with pre-pended header. As described above, MAC addresses originating on MC-LAG local member ports in one Aggregation Switch and transmitted over the VFL are associated in the peer Aggregation Switch with the same MC-LAG because both switches are fully aware of the entire list of MC-LAG member ports. As such, when Aggregation Switch 106 b receives the packet with pre-pended header, it stores the MC-LAG A's aggregate group identifier as associated with the source MAC address MAC_(A). For example, Switching ASIC with MID=45 (and/or Switching ASIC with MID=63) enters into its MAC/HDI forwarding table that source MAC address MAC_(A) is associated with logical aggregate group MC-LAG A.

Though a MAC address request is generally broadcast over every port associated with the VLAN ID, in an embodiment, a loop prevention mechanism prevents broadcast of packets received by an Aggregation Switch 106 over the Virtual Fabric Link 124 over local MC-LAG member ports. Thus, when Aggregation Switch 106 b receives the MAC address request over VFL 124, it will not broadcast copies of the MAC address request over local MC-LAG A member ports L_(A2) and local MC-LAG B member ports L_(B2). This loop prevention mechanism prevents broadcast packet flows originating from Aggregation Switch A from looping to edge Node A and edge Node B through Aggregation Switch B. The loop prevention process thus provides for operation of the multi-chassis system without need of the spanning tree protocol on the MC-LAG member ports.

The Aggregation Switches 106 a and 106 b do not generate a response to the MAC address request because the destination IP address does not correspond to any of its local IP interfaces configured on its local VLANs. However, when edge node B receives the MAC address request (over L_(B1)), it will broadcast the packet to Device B which will then respond. As the response packet, which is a unicast packet, traverses the multi-chassis system to Device A, the source MAC address of Device B is learnt by the Aggregation Switches 106 in a similar process. Device A and Device B now are able to communicate with IP addressing over the Layer 2 multi-path infrastructure provided by the multi-chassis link aggregates. MAC addresses are learned as either associated with a particular port (for the case of fixed ports) or as associated with an aggregate group identifier (for the case of LAGs or MC-LAGs). Since the Aggregation Switches 106 have non-overlapping ranges of hardware device identifiers, MIDs, the hardware device identifiers are unique within the multi-chassis system 140. Using the global unique hardware device identifiers MIDs and external port identifiers, the MAC addresses can be associated with a fixed ports or aggregate group identifier.

FIG. 8 illustrates a schematic block diagram of an embodiment for maintaining the MAC/HDI forwarding tables in the multi-chassis system. The MAC forwarding tables have a default or configured “aging” time for entries. When a MAC address in the MAC/HDI forwarding table has not been updated during the aging time, the entry will be deleted or flushed from the table. In the multi-chassis system however, the aging of entries may create a problem with continuous flooding when packet flows have different paths for the upstream and downstream directions. In order to maintain the MAC forwarding tables synchronized, a multi-chassis system needs to implement a keep-alive mechanism across the entire set of switches that are part of the system. Keep-alive packets are periodic packets (sent at a constant interval equal to the aging timeout parameter). These packets carry a reserved multicast destination MAC address to allow the packets to be flooded to all Switching ASIC devices 210 within all NIMs 152 in the multi-chassis system. The source MAC address of the packets is equal to the MAC address of each entry learned within the MAC forwarding table. As a result of this mechanism, a given MAC address will not age and be deleted or flushed unless it is no longer used in any of the Aggregation Switches within the multi-chassis system.

To avoid eternal MAC addresses (e.g., an address that will not age so as to be flushed or deleted), a MAC entry is assigned an “owner” or responsible module within the multi-chassis system. The owner of a MAC entry is generally a particular NIM 152. The MAC ownership is determined in different ways. For example, the MAC ownership may depend on the type of port on which it was first learned as follows. For MAC addresses associated with fixed ports, the Switching ASIC device 210 that contains the external port where the MAC address traffic was received is the owner of the MAC entry and controls the aging of the MAC address. Other Switching ASICs 210 learn this MAC address upon reception of a packet with a pre-pended header. The NIMs 152 that host such Switching ASIC devices 210 will not become owners of the MAC entry. A device becomes the owner of a MAC entry related to a fixed port only when it learned that address on from an external port interface.

For MAC addresses learned on aggregate ports (i.e. LAG or MC-LAG), the owner of a MAC address is determined by a similar mechanism as described for the fixed ports. The difference here is that the Switching ASICs 210 typically provide an additional feature called remote or local bit. This bit is only set when an entry is created and it never changes its value during the lifetime of a MAC entry. The local bit is set (i.e. local=1 or remote=0) only when: a) The entry does not already exist; b) A packet is received on a front panel port, e.g. there is no pre-pended header present. As a result of this approach, there will always be a single Switching ASIC device 210 in the system whose local bit is set. That NIM 152 hosting that Switching ASIC device 210 becomes the owner of this MAC address and hence responsible for the generation of keep-alive packets.

The NIMs 152 coordinate deleting an entry from the MAC/HDI forwarding tables. As shown in FIG. 8, a logical inter-process communication connection (IPC) 310 is created between the CMMs 150 a and 150 b of the Aggregation Switches 106. The same logical connections exist between any pair of NIMs 152. The IPC 310 may be created over the VFL 124 or over a LAN connection. When one of the NIMs 152 of a local Aggregation Switch 106 a receives a flush message for a MAC address, it may decide to transmit the flush message to each of the other NIMs 152 a-n on the local and remote Aggregation Switches 106 a/b. The MAC/HDI tables in the Switching and/or Queuing ASICs in the NIMs 152 a-n then flush the entry for the corresponding MAC address. The decision to whether delete the entry locally or not depends on the entry's ownership and type of port where the MAC entry was learned. Entries learned on fixed ports or ordinary aggregates (i.e. LAG) are flushed (and the corresponding event propagated) only if the flush request was received on the NIM 152 that owns the entry. Entries learned on MC-LAG aggregates are only flushed (and the flush event propagated) if there are no active/operational ports that are members of the aggregate neither in the local switch nor on the remote switch.

CMM 150 a-b and NIMs 152 a-n are aware of the entire list of MC-LAG member ports and their states (active/inactive) in the multi-chassis system. When the flush message includes a local port identifier (e.g., gport values) that is valid only on the local Aggregation Switch, the NIM 152 that owns that MAC address being deleted converts the local port identifier to a global port identifier (e.g. MID or modid and device port values) and then transmits the flush message over the IPC to the other NIMs 152 a-n of the local and remote Aggregation Switches 106 a/b. The flushing requests may be triggered by distinct events such a port interface status notifications (e.g. port down) or via explicit management request. For example, when CMM 150 a receives a ‘no mac-learning dynamic’ management message or a static MAC address is deleted upon user request, and the flush allowance requirements describer earlier are met, then the CMM 150 a transmits a flush message with the MAC address to NIMs 150 a-n of Aggregation Switch 106 a and to CMM 150 b of the remote Aggregation Switch 106 b.

FIG. 9 illustrates a schematic block diagram of an embodiment of a pre-pended header of a packet in the multi-chassis system. The pre-pended header 300 includes fields for source HDI 302, destination HDI 304, VLAN ID 306, packet type 308, source MAC address 310 and destination MAC address 312. In an embodiment, the pre-pended header may also include load balance identifier 314 and packet priority 316. The destination HDI 304 includes, for example, the port identifier and MID of a Switching ASIC (e.g. MID=24, port ID=5 or MID=54, device port=12), of either the local or peer Aggregation Switch, associated with the destination MAC address. In another embodiment, the destination hardware device information may include the global port value (GPV) of the external port interface associated the destination MAC address. The destination hardware device information may also include MID of the Switching ASIC connected to the VFL, NIMs, Queuing ASICs, etc. The source HDI 302 may include the MID of the Switching ASIC and the port identifier (e.g., device port) and/or global port value (GPV) of the external port interface. The load balance identifier 314 is used to help the Queueing ASIC to decide which VFL member port to be used as a transit/gateway port to reach the peer Aggregation Switch. The packet priority 316 is used by the Queueing ASIC to determine the specific priority queue.

FIG. 10 illustrates a schematic block diagram for managing inter-process communication within an Aggregation Switch of a multi-chassis system. The Aggregation Switch 106 includes a network of processors connected over a physical medium used for inter-processor communication, referred to as its “system network.” As shown in FIG. 10, the system network includes the Fabric IC 214 and an Ethernet backplane coupled between the chassis management modules CMM-A 150 a and CMM-B 150 b and the NIMs 152. In order to provide for multi-chassis inter-process communication (MCIPC) between the Aggregation Switch 106 and another Aggregation Switch in the multi-chassis system, physical connections must be made between the Aggregation Switches' respective system networks.

To support the physical connectivity, each NIM 152 (only one of which is shown in FIG. 10 for simplicity) provides ports for inter-connecting customer devices, referred to as its “customer-facing ports (CFP)” 408. The CFPs are located on a sub-set of the NIMs making up the system network. In addition, a sub-set of the CFPs are used to physically connect the Aggregation Switches. For example, as shown in FIG. 10, CFP 408 a and CFP 408 b are shown connected to the Virtual Fabric Link 124, which provides the physical connection to the remote Aggregation Switch.

However, the system network must be physically isolated from external networks for security reasons. In order to preserve the isolation between the external networks and the system network, the CFP's coupled to the VFL 124 are assigned to an inter-process communication virtual local-area network (IPC VLAN) to which no other external CFPs may be assigned. This preserves the physical separation from the undesired external networks.

In addition to the CFPs 408 a and 408 b that are coupled to the VFL 124, each NIM 152 further includes internal ports 410 a and 410 b that are assigned to the IPC VLAN. For example, as shown in FIG. 10, each NIM 152 includes Switching ASICs 210 a and 210 b, each of which have a respective internal port 410 a and 410 b coupled thereto. The internal ports 410 a and 410 b provide connectivity between the Switching ASICs 210 a and 210 b, the NIM processor (CPU 404) and the CMMs (CMM-A 150 a and CMM-B 150 b).

In particular, each CMM (CMM-A 150 a and CMM-B 150 b) includes a respective processor (CPUs 402 a and 402 b) and a respective Ethernet switch 400 a and 400 b, which are coupled together via the system network. Within the NIM 152, a first 3-port Ethernet switch 406 a is placed between an Ethernet port of the NI processor 404 and the primary system network Ethernet switch 400 a, one port going to each. The third port of the 3-port Ethernet switch 406 a is connected to the internal port on the Switching ASIC 210 a. Likewise, a second 3-port Ethernet switch 406 b is placed between the Ethernet port of the NI processor 404 and the secondary system network Ethernet switch 400 b, one port going to each. The third port of the 3-port Ethernet switch 406 a is connected to the internal port on the Switching ASIC 210 b. Communication between the Switching ASIC's 210 a and 210 b, CMM processors 402 a, 402 b and NIM processor 404 occurs via the 3-port switches 406 a and 406 b and over the Fabric IC via respective queueing ASIC's 212 a and 212 b. It should be noted that all of the internal HiGig ports between the switching ASIC's 210 a and 210 b and the respective queuing ASICs 212 a and 212 b are also members of the IPC VLAN to permit connectivity while preserving the isolation from external networks.

In addition to providing physical connectivity for the IPC VLAN, each Aggregation Switch also uses a collection of logical addressing schemes to permit applications within the Aggregation Switches to address one another across the VFL 124 (e.g., Ethernet, IP addresses). Since each system network on each Aggregation Switch is internally isolated, the same static (local) addresses may be used on all Aggregation Switches. This conserves address space, simplifies initialization, improves performance and assures that the local addresses are only unique within an Aggregation Switch and not outside it. However, for MCIPC, the logical addressing schemes need to be extended to support addressing between the system networks of the respective Aggregation Switches by creating globally unique addresses (unique among the collection of system networks in the multi-chassis environment).

Therefore, an overlay network is created providing globally unique addresses for each NI processor 404. The addresses are made globally unique by incorporating the respective Aggregation Switches' unique chassis identifier into their values. The globally unique addresses are used for inter-Aggregation Switch communication and do not replace the static (local) addresses. In an embodiment, the local addresses may continue to be used for intra-Aggregation Switch communication. To discover the globally unique addresses of the CMM and NI processors on the remote Aggregation Switch, the CMM processors 402 a and 402 b can create static ARPs for the remote IP addresses with the correct corresponding Ethernet addresses.

However, creation of the overlay network may require that each NI processor 404 support multiple address values for each of its addressing schemes. In addition, to prevent loops, only one VFL CFP (e.g., port 408 a) may be active on each Aggregation Switch 106 at any point in time and may be referred to as the “primary” port. Furthermore, filters may need to be created on the VFL CFPs 408 a and 408 b to prevent traffic carrying static, locally-unique addresses from leaking through between Aggregation Switches. For example, the filtering capabilities of the Switching ASICs 210 a and 210 b can be modified so that any packet with a source Ethernet address that is only locally unique is not forwarded when received on the primary port.

FIG. 11 illustrates a schematic block diagram of an embodiment for implementing inter-processes communication between the Aggregation Switches 106 a and 106 b in accordance with the present invention. As can be seen in FIG. 11, one of the CFP's coupled to the VFL 124 on Aggregation Switch 106 a is designated as the primary port 408 ap, and likewise, there is a primary port 408 bp on Aggregation Switch 106 b. The primary ports 408 ap and 408 bp do not need to be physically coupled over the same link, as shown in FIG. 11.

In an embodiment, although all VFL member ports are members of the IPC VLAN, packets within the IPC VLAN are only allowed to exit the primary port 408 ap and 408 bp of each Aggregation Switch 106 a and 106 b towards the VFL. However, packets must be able to be received on any VFL member port. This enables the Aggregation Switches 106 a and 106 b to designate a new primary port, if necessary. When a new primary port is selected, in an embodiment, the NI processor 404 hosting that port generates proxy packets for each of the remote Aggregation Switches' 106 a and 106 b globally unique Ethernet addresses to update their forwarding tables. In addition, only one port 410 of the type connecting the 3-port switch 406 to the switching ASIC 210 is active in the chassis at a given time. This port is selected by being the one residing on the same NIM as the “primary port” and connected to the Ethernet Switch 400 of the currently active CMM. This will always be the source port of packets egressing over the VFL 124.

In the example shown in FIG. 11, port 408 ap is the primary port coupled to Switching ASIC 210 b on network interface module NI-1. Packets to be routed over the VFL must exit port 408 ap. For example, a packet with a globally unique destination address can be routed to Ethernet Switch-X 400 via the system network, which can then forward the packet to Switching ASIC 210 a via 3-Port Switch 406 and internal port 410 on NI-1. Switching ASIC 210 a can forward the packet to Switching ASIC 210 b via queuing ASIC 212 a, fabric IC 214 a and queuing ASIC 212 b. Since the packet has a globally unique destination address, Switching ASIC 210 b will forward the packet over the VFL 124 to Switching ASIC 210 c on Aggregation Switch 106 b, which can forward the packet internally on Aggregation Switch 106 b via queuing ASIC 212 c.

Likewise, port 408 bp is the primary port coupled to Switching ASIC 210 d on network interface module NI-4 of Aggregation Switch 106 b. Packets to be routed over the VFL must exit port 408 bp. For example, a packet with a globally unique destination address can be routed to Ethernet Switch-Y 400 via the system network, which can then forward the packet to Switching ASIC 210 d via the respective 3-Port Switch 406 on NI-4 and internal port 410 on NI-4. Since the packet has a globally unique destination address, Switching ASIC 210 d will forward the packet over the VFL 124 to Switching ASIC 210 e on Aggregation Switch 106 a, which can forward the packet internally on Aggregation Switch 106 a via queuing ASIC 212 e.

FIG. 12 illustrates an exemplary packet flow for a multi-chassis inter-process communication. As shown in FIG. 12, a packet 420 is originated at the NI processor 404 of network interface module NI-5, with a source address of MAC@A5 having the chassis identifier for Aggregation Switch 106 a incorporated therewith and a destination address of MAC@B6 having the chassis identifier for Aggregation Switch 106 b incorporated therewith. The packet 420 is forwarded over the system network, where it is received at port 5 on Ethernet Switch-X 400 within CMM-A1 150. Ethernet Switch-X 400 learns the source address of the packet at port 5 and updates its MAC table 250 a with this information. Ethernet Switch-X further forwards the packet out port 20 to CPU-X 402 within CMM-A1 150, where the packet dies since CPU-X is not the destination address of the packet. Ethernet Switch-X 400 also forward the packet out ports 1 and 3 towards NI-1 and NI-3, respectively.

The packet dies upon reaching the CPU 404 and Switching ASIC 210 e of NI-3 since the destination address is not NI-3 and NI-3 does not have the primary port 408 ap. At NI-1, the packet reaches the 3-Port switch 406, which forwards the packet to Switching ASIC 210 a and CPU 404 of NI-1. The packet dies upon reaching CPU 404 of NI-1, since this is not the destination address of the packet. However, Switching ASIC 210 a forwards the packet to queuing ASIC 212 a of NI-1, which forwards the packet to the fabric IC 214 a. The fabric IC 214 a floods the packet at each NIM 152 of Aggregation Switch 106 a. The packet dies at the queuing ASIC of each NIM except for the queuing ASIC 212 b coupled to the Switching ASIC 210 b having the primary port 408 ap on NI-1. Upon reaching the Switching ASIC 210 b, the packet is forwarded on the VFL 124 over to the remote Aggregation Switch 106 b.

At the remote Aggregation Switch 106 b, the packet 420 is received at Switching ASIC 210 c on NI-2 and forwarded by queuing ASIC 212 c on NI-2 over the fabric IC 214 b to be flooded at each NIM 152 on the remote Aggregation Switch 106 b. The packet dies at each queuing ASIC of each NIM except for the queuing ASIC 212 d coupled to the Switching ASIC 210 d having the primary port 408 bp on NI-4. Upon reaching the Switching ASIC 210 d, the packet 420 is forwarded via the 3-Port Switch 406 of NI-4 to Ethernet Switch-Y 400 within CMM-A2 150 of Aggregation Switch 106 b. The packet is also forwarded back across the VFL 124 to Aggregation Switch 106 a. However, the hardware (Switching ASIC) on Aggregation Switches 106 a and 106 b provide a filter that only allows a packet to flood out the ports on which it did not originate. However, the port on which the packet originated is the only port that is not blocked. Therefore, after looping back, the packet is dropped.

At Ethernet Switch-Y 400, the packet is received at port 4 and forwarded out port 20 to CPU-Y 402 within CMM-A2 150, where the packet dies since CPU-Y is not the destination address of the packet. Ethernet Switch-Y 400 also forwards the packet out ports 2 and 6 towards NI-2 and NI-6, respectively. The packet dies upon reaching the CPU 404 and Switching ASIC 210 of NI-2 since the destination address is not NI-2 and NI-2 does not have the primary port 408 bp. At NI-6, the packet is forwarded to the CPU 404, which recognizes the destination address as its address and processes the received packet. In addition, Ethernet Switch-Y updates its MAC table 250 b with the MAC address of NI-5 being associated with port 4.

The network interface modules 152 and chassis management modules 150 each include one or more processing devices, such as a microprocessor, micro-controller, digital signal processor, microcomputer, central processing unit, field programmable gate array, programmable logic device, state machine, logic circuitry, analog circuitry, digital circuitry, and/or any device that manipulates signals (analog and/or digital) based on hard coding of the circuitry and/or operational instructions. The NIMs 152 and CMMs 150 also include a memory that is an internal memory or an external memory. The memory may be a single memory device or a plurality of memory devices. Such a memory device may be a read-only memory, random access memory, volatile memory, non-volatile memory, static memory, dynamic memory, flash memory, cache memory, and/or any device that stores digital information. In addition, the NIMs 152 and CMMs 150 may implement one or more of their functions via a state machine, analog circuitry, digital circuitry, and/or logic circuitry, the memory storing the corresponding operational instructions may be embedded within, or external to, the circuitry comprising the state machine, analog circuitry, digital circuitry, and/or logic circuitry. Furthermore, the NIMs 152 and CMMs 150 may execute hard-coded and/or software and/or operational instructions stored by the internal memory and/or external memory to perform the steps and/or functions described herein and may be implemented in a single or in one or more integrated circuits.

As may be used herein, the terms “substantially” and “approximately” provides an industry-accepted tolerance for its corresponding term and/or relativity between items. Such an industry-accepted tolerance ranges from less than one percent to fifty percent and corresponds to, but is not limited to, component values, integrated circuit process variations, temperature variations, rise and fall times, and/or thermal noise. Such relativity between items ranges from a difference of a few percent to magnitude differences. As may also be used herein, the term(s) “coupled to” and/or “coupling” and/or includes direct coupling between items and/or indirect coupling between items via an intervening item (e.g., an item includes, but is not limited to, a component, an element, a circuit, and/or a module) where, for indirect coupling, the intervening item does not modify the information of a signal but may adjust its current level, voltage level, and/or power level. As may further be used herein, inferred coupling (i.e., where one element is coupled to another element by inference) includes direct and indirect coupling between two items in the same manner as “coupled to”. As may be used herein, the term “operable to” indicates that an item includes one or more of processing modules, data, input(s), output(s), etc., to perform one or more of the described or necessary corresponding functions and may further include inferred coupling to one or more other items to perform the described or necessary corresponding functions. As may also be used herein, the term(s) “connected to” and/or “connecting” or “interconnecting” includes direct connection or link between nodes/devices and/or indirect connection between nodes/devices via an intervening item (e.g., an item includes, but is not limited to, a component, an element, a circuit, a module, a node, device, etc.). As may further be used herein, inferred connections (i.e., where one element is connected to another element by inference) includes direct and indirect connection between two items in the same manner as “connected to”.

Embodiments have also been described above with the aid of method steps illustrating the performance of specified functions and relationships thereof. The boundaries and sequence of these functional building blocks and method steps have been arbitrarily defined herein for convenience of description. Alternate boundaries and sequences can be defined so long as the specified functions and relationships are appropriately performed. Any such alternate boundaries or sequences are thus within the scope and spirit of the claimed invention. Similarly, flow diagram blocks may also have been arbitrarily defined herein to illustrate certain significant functionality. To the extent used, the flow diagram block boundaries and sequence could have been defined otherwise and still perform the certain significant functionality. Such alternate definitions of both functional building blocks and flow diagram blocks and sequences are thus within the scope and spirit of the claimed invention. One of average skill in the art will also recognize that the functional building blocks, and other illustrative blocks, modules and components herein, can be implemented as illustrated or by one or multiple discrete components, networks, systems, databases or processing modules executing appropriate software and the like or any combination thereof. 

What is claimed is:
 1. An Aggregation Switch in a multi-chassis system, comprising: an internal system network; and a plurality of network interface modules coupled to the system network, each of the plurality of network interface modules including at least one respective customer-facing port, a sub-set of the customer-facing ports being assigned to an inter-process communication virtual local area network (IPC VLAN) and coupled to a virtual fabric link (VFL); wherein the VFL is connected to a remote Aggregation Switch in the multi-chassis system; wherein each of the Aggregation Switch and the remote Aggregation Switch are active, the remote Aggregation Switch being in a separate physical chassis; wherein the IPC VLAN enables the plurality of network interface modules to communicate with the remote Aggregation Switch via the system network and the VFL; wherein each of the plurality of network interface modules has a globally unique address associated therewith that is unique between the Aggregation Switch and the remote Aggregation Switch, the globally unique address being used for communication between the Aggregation Switch and the remote Aggregation Switch; wherein each of the plurality of network interface modules further has a local address associated therewith for communication between the plurality of network interface modules on the Aggregation Switch; and wherein the Aggregation Switch has a chassis identifier that uniquely identifies the Aggregation Switch between the Aggregation Switch and the remote Aggregation Switch, the globally unique address for each of the plurality of network interface modules including the respective local address and the chassis identifier.
 2. The Aggregation Switch of claim 1, wherein: one of the sub-set of the customer-facing ports coupled to the VFL is designated as a primary port on which all IPC VLAN packets destined for the remote Aggregation Switch are transmitted.
 3. The Aggregation Switch of claim 1, further comprising: a chassis management module coupled to the system network, the IPC VLAN further enabling communication between the plurality of network interface modules and the chassis management module over the system network and enabling communication between the chassis management module and an additional chassis management module on the remote Aggregation Switch via the system network and the VFL.
 4. The Aggregation Switch of claim 3, wherein each of the plurality of network interface modules further includes: a switching application specific integrated circuit (ASIC) having an internal port coupled thereto, the internal port being assigned to the IPC VLAN and coupling the switching ASIC to the chassis management module.
 5. The Aggregation Switch of claim 4, wherein each of the plurality of network interface modules further includes: a network interface processor; and a three-port switch coupled between the network interface processor and the internal port of the switching ASIC, the three-port switch further coupled to the chassis management module via the system network to enable communication between the switching ASIC, the network interface processor and the chassis management module via the IPC VLAN.
 6. The Aggregation Switch of claim 5, wherein the chassis management module (CMM) includes: a CMM processor; and an Ethernet switch coupled to the CMM processor and the three-port switch of each of the plurality of network interface modules.
 7. The Aggregation Switch of claim 5, wherein the internal system network further includes: switching fabric coupled to each of the plurality of network interface modules for enabling communication between the switching ASIC of each of the plurality of network interface modules.
 8. The Aggregation Switch of claim 5, further comprising: a secondary chassis management module coupled to the chassis management module, and wherein each of the plurality of network interface modules further includes: an additional switching ASIC; and an additional three-port switch coupled between the network interface processor and the additional switching ASIC and further coupled to the secondary chassis management module.
 9. The Aggregation Switch of claim 1, wherein each of the plurality of network interface modules includes a filter to prevent packets addressed to one of the local addresses from being sent over the VFL to the remote Aggregation Switch.
 10. The Aggregation Switch of claim 1, wherein each of the plurality of network interface modules uses the respective globally unique address as the source address of a packet when sending the packet to the remote Aggregation Switch.
 11. A method for multi-chassis inter-process communication (IPC) within a multi-chassis system, comprising: generating a packet at a first network interface module of a first Aggregation Switch destined for a second network interface module of a second Aggregation Switch, the first Aggregation Switch and the second Aggregation Switch forming a multi-chassis system, the first Aggregation Switch and the second Aggregation Switch both being active and each in a separate physical chassis; incorporating a first chassis identifier of the first Aggregation Switch into a source address of the first network interface module to produce a globally unique source address and a second chassis identifier of the second Aggregation Switch to a destination address of the second network interface module to produce a globally unique destination address; transmitting the packet over an internal system network of the first Aggregation Switch, the internal system network forming an inter-process communication virtual local area network (IPC VLAN) to a primary customer-facing port (CFP) of the IPC VLAN, the primary CFP of the IPC VLAN being coupled to a virtual fabric link (VFL), the VFL connecting the first Aggregation Switch to the second Aggregation Switch in the multi-chassis system; and transmitting the packet over the VFL for internal routing within the second Aggregation Switch to the second network interface module.
 12. The method of claim 11, wherein the transmitting the packet over the internal system network further includes: transmitting the packet over the internal system network to a chassis management module coupled thereto; wherein the IPC VLAN further enabling communication between the plurality of network interface modules and the chassis management module over the system network and enabling communication between the chassis management module and an additional chassis management module on the remote Aggregation Switch via the system network and the VFL.
 13. The method of claim 12, wherein the generating the packet further includes: generating the packet at a network interface processor of the first network interface module.
 14. The method of claim 13, wherein the transmitting the packet over the internal system network further includes: transmitting the packet to the chassis management module via a three-port switch coupled between the network interface processor and the chassis management module, the three-port switch further coupled to a switching application specific integrated circuit (ASIC) having an internal port coupled thereto, the internal port being assigned to the IPC VLAN and coupling the switching ASIC to the chassis management module.
 15. The method of claim 14, wherein the transmitting the packet over the internal system network further includes: transmitting the packet over switching fabric coupled to each of a plurality of network interface modules within the first Aggregation Switch to forward the packet to a primary switching ASIC coupled to the primary CFP.
 16. The method of claim 11, wherein the source address of the first network interface module is a local address associated therewith for communication between a plurality of network interface modules on the first Aggregation Switch, each of the plurality of network interface modules having a respective local address associated therewith.
 17. The method of claim 16, further comprising: preventing additional packets addressed to or from one of the local addresses from being sent over the VFL to the remote Aggregation Switch. 